From: Florian Müllner <fmuellner@gnome.org>
Date: Fri, 18 May 2012 14:04:47 +0000 (+0200)
Subject: panel: Check for appMenu button's reactivity before opening
X-Git-Tag: archive/raspbian/50.5-1+rpi1~1^2~1013^2^2~6588
X-Git-Url: https://dgit.raspbian.org/%22http://www.example.com/cgi/%22/%22http:/www.example.com/cgi/%22?a=commitdiff_plain;h=82c2f5221d96daccae9272496088eb704b4804cc;p=gnome-shell.git

panel: Check for appMenu button's reactivity before opening

When the appMenu is not available, for instance when no windows are
open (on the current workspace), we make its actor unreactive to
"hide" it from keynav. However the menu can still be triggered
erroneously when using the corresponding keyboard shortcut, so
add a check for the actor's reactivity there as well.

https://bugzilla.gnome.org/show_bug.cgi?id=676316
---

diff --git a/js/ui/panel.js b/js/ui/panel.js
index 329f118fc..772bc7706 100644
--- a/js/ui/panel.js
+++ b/js/ui/panel.js
@@ -1115,8 +1115,8 @@ const Panel = new Lang.Class({
 
     openAppMenu: function() {
         let menu = this._appMenu.menu;
-        if (Main.overview.visible || menu.isOpen)
-          return;
+        if (!this._appMenu.actor.reactive || menu.isOpen)
+            return;
 
         menu.open();
         menu.actor.navigate_focus(null, Gtk.DirectionType.TAB_FORWARD, false);